home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: twix.unx.sas.com!walker
- From: walker@twix.unx.sas.com (Doug Walker)
- Subject: Re: Is this a SAS/C bug or have I coded it wrong?
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DL6J8s.M1G@unx.sas.com>
- Date: Sun, 14 Jan 1996 16:31:40 GMT
- X-Nntp-Posting-Host: twix.unx.sas.com
- References: <4cfrc5$gsc@misery.millcomm.com> <4cm9kc$kf7@news.isc.rit.edu> <DKu1Cw.93w@unx.sas.com> <volker.0e5e@vb.franken.de>
- Organization: SAS Institute Inc.
-
- In article <volker.0e5e@vb.franken.de>,
- Volker Barthelmann <volker@vb.franken.de> wrote:
- >Doug Walker (walker@twix.unx.sas.com) wrote:
- >: In article <4cm9kc$kf7@news.isc.rit.edu>, <mjp3783@alpha.isc.rit.edu> wrote:
- >: >> tmpbuf[10];
- >: >>
- >: >I assume this was a mis-type and that this should have been:
- >: >int tmpbuf[10];
- >:
- >: Not really, the two are exactly equivalent. If no type is
- >: provided on variable's definition in ANSI C, "int" is
- >: assumed.
- >
- >Are You sure about that? I was under the impression that ANSI C required
- >at least a type-specifier, type-qualifier or storage-class-specifier for
- >a declaration.
- >
- >Volker
- >
-
- No, I'm not 100% sure; I'd have to look it up in the standard,
- which I don't have handy right now.
-
-
- --
- ***** / walker@unx.sas.com
- *|_o_o|\\ Doug Walker< BIX, Portal: djwalker
- *|. o.| || \ AOL: weissblau
- | o |//
- ======
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-